We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When using ZFS, cgroups do not correctly account for written data (and, possibly, prefetched read data). Give a look here:
This could be fixed by using normal /proc/pid stats rather than cgroups for gathering these info.
/proc/pid
Use classical /proc/pid stats for VM and container statistics.
really want
No response
The text was updated successfully, but these errors were encountered:
Hey, @shodanshok. Do you have DefaultIOAccounting=yes in /etc/systemd/system.conf? This fixed the problem for me on my Proxmox servers with ZFS.
DefaultIOAccounting=yes
/etc/systemd/system.conf
After enabling IO accounting:
sudo systemctl daemon-reexec
Sorry, something went wrong.
I think this request is wontfix because it will not work for qemu VMs.
@ilyam8 yes, I tried DefaultIOAccounting=yes (and systemctl daemon-reexec + reboot) but nothing changed on my Rocky Linux 9.4. Any idea?
systemctl daemon-reexec
reboot
Accounting via /proc/[pid] should work for qemu VMs: while IO is done a dedicated threads, the counters under /proc/[pid]/ioseem to account for them.
/proc/[pid]
/proc/[pid]/io
No branches or pull requests
Problem
When using ZFS, cgroups do not correctly account for written data (and, possibly, prefetched read data). Give a look here:
This could be fixed by using normal
/proc/pid
stats rather than cgroups for gathering these info.Description
Use classical
/proc/pid
stats for VM and container statistics.Importance
really want
Value proposition
Proposed implementation
No response
The text was updated successfully, but these errors were encountered: